Add tracking of query call locations#154402
Conversation
This comment has been minimized.
This comment has been minimized.
f641c01 to
4197e18
Compare
This comment has been minimized.
This comment has been minimized.
4197e18 to
3ac1303
Compare
|
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Add tracking of query call locations
This comment has been minimized.
This comment has been minimized.
|
Finished benchmarking commit (e18d7fc): comparison URL. Overall result: ❌ regressions - please read the text belowBenchmarking this pull request means it may be perf-sensitive – we'll automatically label it not fit for rolling up. You can override this, but we strongly advise not to, due to possible changes in compiler perf. Next Steps: If you can justify the regressions found in this try perf run, please do so in sufficient writing along with @bors rollup=never Instruction countOur most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.
Max RSS (memory usage)Results (secondary -1.5%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (secondary 0.9%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 485.545s -> 486.608s (0.22%) |
|
☔ The latest upstream changes (presumably #154304) made this pull request unmergeable. Please resolve the merge conflicts. |
|
Overhead seems a bit on the high side to have on by default.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
This adds tracking of query call locations using
#[track_caller]in additional to associating query calls with a span.Query call locations are printed for query panic stack traces and for
-Z verbose-internals. The latter being helpful to track down accidental query cycles.